Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update to pg_partman 5.2.4 #24

Merged
merged 1 commit into from
Jan 16, 2025
Merged

Update to pg_partman 5.2.4 #24

merged 1 commit into from
Jan 16, 2025

Conversation

BCook98
Copy link
Contributor

@BCook98 BCook98 commented Jan 16, 2025

pg_partman 5.2.0 adds support for partitioning by UUIDv7s

Replicated the changed made in 7b9ebd6

@BCook98
Update to pg_partman 5.2.4
09a8ee6 
[pg_partman 5.2.0](https://github.com/pgpartman/pg_partman/releases/tag/v5.2.0) adds support for partitioning by UUIDv7s

Replicated the changed made in dbsystel@7b9ebd6
jschirrmacher
jschirrmacher approved these changes Jan 16, 2025
View reviewed changes
Copy link
Contributor

@jschirrmacher jschirrmacher left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your PR!

@Morl99
Copy link
Contributor

Morl99 commented Jan 16, 2025

@jschirrmacher the actions are not allowed to publish the temporary image. This is either to changes due to the new synchronization of settings by the global gitlab repo or due to the fact that the source code originates from a fork.

@Morl99
Copy link
Contributor

Morl99 commented Jan 16, 2025

@jschirrmacher the actions are not allowed to publish the temporary image. This is either to changes due to the new synchronization of settings by the global gitlab repo or due to the fact that the source code originates from a fork.

I am rerunning the action to rule out a temporary problem.

@Morl99
Copy link
Contributor

Morl99 commented Jan 16, 2025

@jschirrmacher the actions are not allowed to publish the temporary image. This is either to changes due to the new synchronization of settings by the global gitlab repo or due to the fact that the source code originates from a fork.

I am rerunning the action to rule out a temporary problem.

Since this change cannot be the source of the problems, we could merge it and see if the workflow runs fine on main.

@Morl99 Morl99 merged commit b42c1ed into dbsystel:main Jan 16, 2025
0 of 9 checks passed
@Morl99 Morl99 mentioned this pull request Jan 16, 2025
Open
@Morl99
Copy link
Contributor

Morl99 commented Jan 16, 2025 •
edited
Loading

The workflow ran fine on main, the newest images now contains the latest version.

We can follow up on the problems in #25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jschirrmacher jschirrmacher jschirrmacher approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@BCook98 @Morl99 @jschirrmacher